<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><title>Velocityme Minutes 17</title></head>

<body>
         
<h1>Velocityme Minutes 19</h1>
         
<table cellpadding="2" cellspacing="0" border="1" width="100%">
       <tbody>
         <tr>
           <th valign="top" bgcolor="#cccccc">Date<br>
           </th>
           <th valign="top" bgcolor="#cccccc">Venue<br>
           </th>
           <th valign="top" bgcolor="#cccccc">Present<br>
           </th>
           <th valign="top" bgcolor="#cccccc">Apologies<br>
           </th>
         </tr>
         <tr>
           <td valign="top">2002-12-30<br>
           </td>
           <td valign="top">22 Bordeaux,<br>
   Tokia <br>
           </td>
           <td valign="top">Robert Crida<br>
     Barry Kingston<br>
           </td>
           <td valign="top">David Spencer<br>
   Wayne Paverd<br>
           </td>
         </tr>
                   
  </tbody>     
</table>
         
<h2>Agenda</h2>
         
<ol>
       <li>Acceptance of &nbsp;previous minutes</li>
     <li>Class design for UI</li>
     <li>SQL Object<br>
     </li>
     <li>History and auditing, Permission, Role, User Access, Notes, Attachments,
 Hyperlinks and Template Task Trees</li>
    <li>SQL Tutorial for RC</li>
    <li>Looking Back<br>
    </li>
         
</ol>
         
<h2></h2>
   <br>
     
<table cellpadding="2" cellspacing="2" border="1" width="100%">
     <tbody>
       <tr>
         <th valign="top" bgcolor="#cccccc">Topic<br>
         </th>
         <th valign="top" bgcolor="#cccccc">Responsibility<br>
         </th>
         <th valign="top" bgcolor="#cccccc">Date<br>
         </th>
       </tr>
       <tr>
         <td valign="top">1. Minutes were accepted<br>
         </td>
         <td valign="top"><br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">2. RC show what had been done, but said that he 
would look at it some more<br>
  RC Thinks that a strategy isrequired for the UI to avoid unnecessary faffing.<br>
         </td>
         <td valign="top">RC<br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">3. A discussion was had about the SQL Object and
 BR will continue with it but will stream line it to initially work with
the  SELECT statement<br>
         </td>
         <td valign="top">BR<br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">4. &nbsp;General Object dicussion<br>
               
      <ol>
          <li>Permission, there was much debate with regards to this object,
 which resulted in the following</li>
                   
        <ol type="a">
            <li>This object will not access teh database<br>
            </li>
            <li>it will contain an inner class which will act like a ENUM 
structure, contain all the possible permissions and strings.</li>
            <li>The method toString() will return the string associated with
 the permission value(index)<br>
            </li>
                   
        </ol>
          <li>History and auditing</li>
                   
        <ol type="a" start="1">
           <li> XML will be used to store deltas for tasks and issues.</li>
           <li>This subject will be discussed again for more clarity.<br>
          </li>
         
        </ol>
          <li><br>
          </li>
               
      </ol>
         </td>
         <td valign="top"><br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">5. SQL Tutorials for RC<br>
         </td>
         <td valign="top"><br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">5.1. BR said that he has got must still bring them 
though<br>
         </td>
         <td valign="top">BR<br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">6. Nothing was discussed</td>
         <td valign="top"><br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">7. Other        </td>
         <td valign="top"><br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">7.1. Action always contain a minimum state machine<br>
 e.g. State machine &nbsp;= Completed, Incomplete<br>
         </td>
         <td valign="top"><br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">7.2. An actions status is determined by its state 
machines current state which is influenced by its children's status'<br>
         </td>
         <td valign="top"><br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">7.3. NB state machines should not have things like 
a design state (Best practice), Use child actions to indicate life cycle
stages<br>
         </td>
         <td valign="top"><br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
       <tr>
         <td valign="top">7.4. ? Are state machines the same for issues and 
actions...<br>
         </td>
         <td valign="top"><br>
         </td>
         <td valign="top"><br>
         </td>
       </tr>
          
  </tbody> 
</table>
 <br>
   <br>
        
<table cellpadding="2" cellspacing="0" border="1" width="100%">
       <tbody>
         <tr>
           <th valign="top" bgcolor="#cccccc">Author<br>
           </th>
           <th valign="top" bgcolor="#cccccc">Date<br>
           </th>
           <th valign="top" bgcolor="#cccccc">Next meeting<br>
           </th>
           <th valign="top" bgcolor="#cccccc">Date<br>
           </th>
         </tr>
         <tr>
           <td valign="top">Barry Radloff<br>
           </td>
           <td valign="top">2003-01-07<br>
           </td>
           <td valign="top">22 Bordeaux Tokai<br>
           </td>
           <td valign="top">2003-01-07<br>
         </td>
         </tr>
                   
  </tbody>     
</table>
     <br>
     <br>
      <br>
   <br>
  <br>
 <br>
</body></html>